Top level definitions

At the top level of a program, a definition
\begin{scheme} (define \hyper{variable} \hyper{expression})% \end{scheme}
has essentially the same effect as the assignment expression
\begin{scheme} (\ide{set!}\ \hyper{variable} \hyper{expression})% \end{scheme}
if variable is bound. If variable is not bound, however, then the definition will bind variable to a new location before performing the assignment, whereas it would be an error to perform a set! on an unbound variable.


\begin{scheme} (define add3 (lambda (x) (+ x 3))) (add3 3) \ev 6 (define first car) (first '(1 2)) \ev 1\end{scheme}

All Scheme implementations must support top level definitions.

Some implementations of Scheme use an initial environment in which all possible variables are bound to locations, most of which contain undefined values. Top level definitions in such an implementation are truly equivalent to assignments.

Rozas: equal time for opposition semantics?